CLImax is a shareware program distributed on a “try-before-you-buy” basis. If you like it and wish to continue using it, print out the form below and send it with a check or money order for $15 US to the address on the form. CLImax is not annoy-ware, nor is it crippled in any way — it is fully functional in its current form. Once your check is in the mail, you may check the box marked “I Paid” inside the preferences box in good conscience, and CLImax will stop reminding you that it’s unregistered shareware.
See the file “Register me!” for more details, and further legal information.
Warranty (or lack thereof)
There is NO WARRANTY, express or implied, for CLImax or any of its supporting files. I've made an effort to get everything to work properly and have it be compatible with as much as possible, but there's always going to be something I've missed. Use this software at your own risk. If you find a bug, drop me a line at athaler@umich.edu and I'll see what I can do.
See the file “Register me!” for more details, and further legal information.
Known Problems
Now on to some of the more important things you need to know about what CLImax can and can’t do.
• If you run into problems with clicks falling through CLImax's window, that’s due to a known bug in the system software. Install the extension “TSM Fix” (included with this package) and the problem should go away.
• Variable troubles: You can set variables to object references — for example, “set fw to ref front window” — which will get freshly resolved every time you use them. However, and this is a problem that’s been bothering me for a while, you can’t set a variable to an object reference containing a “whose” clause — for example,
set cfiles to ref (files of front window whose name ends with ".c")
Well, technically you *can*, but AppleScript (1.1) will overflow its stack space when CLImax tries to save the context, resulting in your losing all changes since it was last saved. I’ve tried to come up with ways to prevent this from happening, but none of them worked very well. This is just something that will have to be lived with until either AppleScript gets fixed or I can come up with an acceptable way around it.
